Skip to content

Conversation

@Robinlovelace
Copy link
Collaborator

No description provided.

@Robinlovelace Robinlovelace requested review from a team and mvl22 March 13, 2024 07:01
@mvl22
Copy link
Member

mvl22 commented Dec 4, 2024

This looks fine, except that it mixes two separate things - the success threshold is not relevant to this ticket. Maybe just needs a rebase. Be good to get this one sorted.

@Robinlovelace
Copy link
Collaborator Author

Oh yes, forgot about this one..

@Robinlovelace Robinlovelace changed the title Remove email option, unused, fix #89 Re-add SuccessThreshold Dec 4, 2024
@Robinlovelace
Copy link
Collaborator Author

Rebased. So the email arg is removed and successThreshold (re?) added.

@Robinlovelace
Copy link
Collaborator Author

Cc @wangzhao0217 can you take a quick look and provide 👍

@Robinlovelace
Copy link
Collaborator Author

Look good to you @mvl22 after rebasing as per commit above?

@mvl22
Copy link
Member

mvl22 commented Dec 4, 2024

I can't actually work out what the resulting commit will be...

As far as I can see the successThreshold changes are still present. I don't think you intended that.

@Robinlovelace
Copy link
Collaborator Author

As far as I can see the successThreshold changes are still present. I don't think you intended that.

Yes I intended for that. We don't have access to that parameter at the moment. As you will see in the updated title of this PR its purpose now is to add that parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parameter emailOnCompletion should not e-mail a junk address by default

3 participants